(Proposed Version 3.0.2, updated 2012-05-12 by AA6YQ and G3ZOD)

ADX XML Schema for Amateur Data Interchange Format (ADIF)

Table of Contents

1. Description

2. Checks not Required

3. Limitations

I. Description

ADIF 3.0.2 introduces ADX as an alternative file format for representing ADIF employing XML syntax.  The ADX XML Schema supplements this, describing ADX using the XML Schema definition language 1.0

The ADX schema can be used to determine whether ADX complies with the ADIF specification.  If used, it must be applied externally without being referenced in the <ADX> root element.

Most aspects of the ADIF specification are validated, subject to some checks that cannot be performed due to being advisory only and others which are not possible or impractical to check.

The schema is available here.

II. Checks not Required

• CONTEST_ID element contents are not validated against the "Contest ID" enumeration because the ADIF field type is "String" (i.e. the enumeration is only advisory).
• CNTY and MY_CNTY element contents are not validated against the "Secondary Administrative Subdivision" enumeration because the enumeration values are controlled by external organizations and so are subject to change without notice..

III. Limitations

• MY_STATE and STATE element contents are not validated against the "Primary Administrative Subdivision" enumeration due to the excessively long regular expression required.
• User-defined field names (contents of the USERDEF element nested in the HEADER element) are not validated against the pre-defined ADIF field names due to the excessively long regular expression required.
• USERDEF elements nested in the HEADER element can optionally have either a RANGE or ENUM attribute but not both; this is not validated.
• Values in FIELDNAME attributes belonging to USERDEF elements nested in a RECORD element are not validated against the USERDEF elements in the HEADER element.
• USERDEF elements nested in RECORD elements do not have their contents validated against the TYPE, RANGE or ENUM (if any) attributes of the corresponding USERDEF element nested in the HEADER element.
• APP element contents are not validated against the TYPE attribute (if any) given.